IP Incident Analysis - 103.250.7.173

(2025-05-12)

Summary :

Review :

Trace Route :

GZ traceroute to 103.250.7.173 (103.250.7.173), 30 hops max, 60 byte packets
 1  10.231.251.2 (10.231.251.2)  0.628 ms
 2  11.73.14.113 (11.73.14.113)  0.533 ms
 3  11.73.17.237 (11.73.17.237)  0.535 ms
 4  11.73.52.97 (11.73.52.97)  0.512 ms
 5  10.102.62.17 (10.102.62.17)  0.837 ms
 6  11.94.153.73 (11.94.153.73)  0.713 ms
 7  11.94.155.97 (11.94.155.97)  1.078 ms
 8  157.148.24.41 (157.148.24.41)  485.266 ms
 9  120.80.137.93 (120.80.137.93)  2.304 ms
10  112.89.0.141 (112.89.0.141)  3.659 ms
11  219.158.6.253 (219.158.6.253)  25.832 ms
12  219.158.30.38 (219.158.30.38)  25.772 ms
13  219.158.8.182 (219.158.8.182)  31.137 ms
14  softbank221111202045.bbtec.net (221.111.202.45)  61.627 ms
15  *
16  *
17  *
18  *
19  *
20  *
21  *
22  *
23  *
24  *
25  *
26  *
27  *
28  *
29  *
30  *

SH traceroute to 103.250.7.173 (103.250.7.173), 30 hops max, 60 byte packets
 1  *
 2  *
 3  11.94.137.45 (11.94.137.45)  0.749 ms
 4  10.102.96.181 (10.102.96.181)  2.283 ms
 5  10.54.37.206 (10.54.37.206)  2.021 ms
 6  *
 7  139.226.204.165 (139.226.204.165)  3.302 ms
 8  *
 9  219.158.19.70 (219.158.19.70)  3.705 ms
10  219.158.8.190 (219.158.8.190)  5.664 ms
11  softbank221111202013.bbtec.net (221.111.202.13)  120.690 ms
12  *
13  *
14  *
15  *
16  *
17  *
18  *
19  *
20  *
21  *
22  *
23  *
24  *
25  *
26  *
27  *
28  *
29  *
30  *

CD traceroute to 103.250.7.173 (103.250.7.173), 30 hops max, 60 byte packets
 1  *
 2  11.73.2.129 (11.73.2.129)  5.401 ms
 3  11.88.170.249 (11.88.170.249)  0.665 ms
 4  45.112.221.2 (45.112.221.2)  0.852 ms
 5  10.54.120.62 (10.54.120.62)  1.273 ms
 6  101.207.253.225 (101.207.253.225)  1.571 ms
 7  119.6.197.57 (119.6.197.57)  5.650 ms
 8  219.158.106.249 (219.158.106.249)  38.149 ms
 9  *
10  219.158.8.174 (219.158.8.174)  44.507 ms
11  softbank221111202013.bbtec.net (221.111.202.13)  97.396 ms
12  *
13  *
14  *
15  *
16  *
17  *
18  *
19  *
20  *
21  *
22  *
23  *
24  *
25  *
26  *
27  *
28  *
29  *
30  *

Server Status : (2025-05-06 14:14   to   2025-05-06 16:16)   Incident time = 2025-05-06 14:44:00  to  2025-05-06 15:46:00

Global Reachability : (2025-05-06 14:14   to   2025-05-06 16:16)   Incident time = 2025-05-06 14:44:00  to  2025-05-06 15:46:00